@thinkingserious @tiwarishubham635 any chance to have a release with this fix?

Hi! I have raised #1099 to fix the failing tests. Will get them merged and then we can review your PR too.

Thanks @tiwarishubham635 :)

HI @gopidesupavan @eladkal
Can you check the failing tests?

HI @gopidesupavan @eladkal Can you check the failing tests?

Sure let me have a look

@tiwarishubham635 thank you for the assistance.
By the way official support for Python 3.12 and 3.13 would be much valued. I see a PR was raised for it #1087

@tiwarishubham635 it looks like python 2.7 is not compatible with latest werkzeug. Just checking 2.7 is way old is it still a requirement to support?

@tiwarishubham635 it looks like python 2.7 is not compatible with latest werkzeug. Just checking 2.7 is way old is it still a requirement to support?

You can do

'werkzeug>=X; python_version < "3.7.0"',
'werkzeug>=Y; python_version >= "3.7.0"'

you just need to find the compatible library versions to match the python versions

@tiwarishubham635 thank you for the assistance. By the way official support for Python 3.12 and 3.13 would be much valued. I see a PR was raised for it #1087

I can check into this and support for latest python versions. However, removing old versions is a tricky part since some of our customers might still be using it. I can check with my team about this decision

I think

install_requires=[
    "werkzeug>=0.11.15,<1.0.0 ; python_version < '3.0'",
    "werkzeug>=0.15.0,<2.0.0 ; python_version >= '3.0' and python_version < '3.6'",
    "werkzeug>=2.0.0,<3.0.0 ; python_version >= '3.6' and python_version < '3.11'",
    "werkzeug>=3.0.0 ; python_version >= '3.11'"
]

should do the trick @gopidesupavan can you try it?

"werkzeug>=0.11.15,<1.0.0 ; python_version < '3.0'",
"werkzeug>=0.15.0,<2.0.0 ; python_version >= '3.0' and python_version < '3.6'",
"werkzeug>=2.0.0,<3.0.0 ; python_version >= '3.6' and python_version < '3.11'",
"werkzeug>=3.0.0 ; python_version >= '3.11'"

Thanks elad for sending this, i was side tracked to another issue.

@tiwarishubham635 can you assist with the tests? I am not sure what is the issue

Looks like MarkupSafe not available in werkzeug. https://github.com/sendgrid/sendgrid-python/actions/runs/14403086591/job/40399477680?pr=1098#step:5:744 mark

Looks like MarkupSafe not available in werkzeug.

I'm not sure why.
@tiwarishubham635 is it really required to support Python 2.7-3.8 ? These are EOL versions.
Also, the CI doesn't really explain if the issue is with specific python version as it doesn't seem to run on all the versions. Is there a way to trigger a run on all versions?

Looks like MarkupSafe not available in werkzeug.

I'm not sure why. @tiwarishubham635 is it really required to support Python 2.7-3.8 ? These are EOL versions. Also, the CI doesn't really explain if the issue is with specific python version as it doesn't seem to run on all the versions. Is there a way to trigger a run on all versions?

Just to check the issue exists due to the eol versions, can yo try removing them from here?

Looks like MarkupSafe not available in werkzeug.

I'm not sure why. @tiwarishubham635 is it really required to support Python 2.7-3.8 ? These are EOL versions. Also, the CI doesn't really explain if the issue is with specific python version as it doesn't seem to run on all the versions. Is there a way to trigger a run on all versions?

Just to check the issue exists due to the eol versions, can yo try removing them from here?

@tiwarishubham635 updated

Alright, looks like it's due to the EOL versions only. Let me check with my team if we can drop the support for these versions

Alright, looks like it's due to the EOL versions only. Let me check with my team if we can drop the support for these versions

Noting that Airflow can not release new versions of sendgrid provider till this is resolved.
apache/airflow#49203

This will impact sendgrid users who uses Airflow. We already got some questions in Airflow chat, I asked the users to contact sendgrid supoort as the sendgrid provider for Airflow is blocked till this fixed is released.

Thanks @tiwarishubham635 any timeline for next release?